System and method for operating a digital storage system

ABSTRACT

A system and method for managing a storage system may include generating, for a data block, a set of tags and a unique name. A set of tags may represent a context. A service related to the data block may be provided in response to receiving at least one of: a tag, a set of tags and a unique name.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 62/701,023, entitled “SYSTEM AND METHOD FOR OPERATING ADIGITAL STORAGE SYSTEM”, filed on Jul. 20, 2018, which is incorporatedherein by reference in its entirety.

FIELD OF THE INVENTION

The present invention relates generally to computer storage systems.More specifically, the present invention relates to a data storageoperating system (OS).

BACKGROUND OF THE INVENTION

Storage of digital content is used by computer applications, users andcomputer systems as known in the art. Digital content is typicallystored in data blocks which may be associated with a user, anapplication, a file or any other object. Typically, to store or retrievedata in/from a storage system, a client needs to specify a reference,e.g., a file name or a physical location on disk.

However, current storage systems and methods do not enable a client tostore, retrieve or manipulate data in a storage system based on alogical context of the data.

SUMMARY OF THE INVENTION

An embodiment for managing a storage system may include generating, fora data block, a set of tags (e.g. a tag set or group) and a unique name;associating the tag set and unique name in a database; receiving arequest including at least one tag; and providing at least one servicerelated to the data block based on the received tag, tag set and uniquename.

An embodiment may store a data block in a storage system and mayassociate information usable for retrieving the data block with theunique name. An embodiment may perform an action related to a data blockbased on matching data in a request with a tag set. An embodiment maydynamically modify a tag set. An embodiment may associate a data blockwith a plurality of tag sets. An embodiment may alert a client based ona registration, the registration including at least one tag.

An embodiment may use tag sets and unique names to automate a procedurerelated to at least one of: data backup, data restore, data copy,periodic maintenance operation and data retention. A unique name may begenerated based on the content of a data block. A service provided by anembodiment may be selected based on a logical context defined by a tagset. A service may be selected based on a rule applied to a set of tagsets.

An embodiment may include a memory and a controller adapted to generate,for a data block, a set of tags (tag set) and a unique name; associatethe tag set and unique name in a database; receive a request includingat least one tag; and provide at least one service related to the datablock based on the received tag, tag set and unique name.

An embodiment may include a unit module (also referred to herein aslayer) adapted to provide an interface with a media storage system basedon a unique name and a data object. The terms “unit”, “module” and“layer” as referred to herein may relate to the same thing and may beused herein interchangeably. An embodiment may include a core layeradapted to generate and maintain tag sets and unique names; a medialayer adapted to store and retrieve data blocks according to uniquenames; and an Application Programming Interface (API) combininginterfaces of the core layer and the media layer. An embodiment mayinclude a controller adapted to store a data block in a storage systemand associate information usable for retrieving the data block with theunique name.

An embodiment may include a controller adapted to provide a data blockbased on matching data in a request with a tag set. An embodiment mayinclude a controller adapted to dynamically modify a tag set. Anembodiment may include a controller adapted to associate a data blockwith a plurality of tag sets. An embodiment may include a controlleradapted to alert a client based on a registration, the registrationincluding at least one tag. An embodiment may include a controlleradapted to use tag sets and unique names to automate a procedure relatedto at least one of: data backup, data restore, data copy, periodicmaintenance operation and data retention. A service may be selectedbased on a context rule applied to a set of tag sets. Other aspectsand/or advantages of the present invention are described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting examples of embodiments of the disclosure are describedbelow with reference to figures attached hereto that are listedfollowing this paragraph. Identical features that appear in more thanone figure are generally labeled with a same label in all the figures inwhich they appear. A label labeling an icon representing a given featureof an embodiment of the disclosure in a figure may be used to referencethe given feature. Dimensions of features shown in the figures arechosen for convenience and clarity of presentation and are notnecessarily shown to scale. For example, the dimensions of some of theelements may be exaggerated relative to other elements for clarity, orseveral physical components may be included in one functional block orelement. Further, where considered appropriate, reference numerals maybe repeated among the figures to indicate corresponding or analogouselements.

The subject matter regarded as the invention is particularly pointed outand distinctly claimed in the concluding portion of the specification.The invention, however, both as to organization and method of operation,together with objects, features and advantages thereof, may best beunderstood by reference to the following detailed description when readwith the accompanied drawings. Embodiments of the invention areillustrated by way of example and not limitation in the figures of theaccompanying drawings, in which like reference numerals indicatecorresponding, analogous or similar elements, and in which:

FIG. 1 shows block diagram of a computing device according toillustrative embodiments of the present invention;

FIG. 2 shows a system according to illustrative embodiments of thepresent invention;

FIG. 3 shows tags associated with a data block according to illustrativeembodiments of the present invention;

FIG. 4 illustrates association of tag sets with a data block nameaccording to illustrative embodiments of the present invention;

FIG. 5 illustrates data in a database according to illustrativeembodiments of the present invention;

FIG. 6 shows a media access layer according to illustrative embodimentsof the present invention;

FIG. 7 shows a write operation according to illustrative embodiments ofthe present invention;

FIG. 8 shows a flow according to illustrative embodiments of the presentinvention;

FIG. 9 shows a system and flows according to illustrative embodiments ofthe present invention;

FIG. 10 shows a system and flows according to illustrative embodimentsof the present invention; and

FIG. 11 shows a prior art system and a system and flows according toillustrative embodiments of the present invention.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of the invention.However, it will be understood by those skilled in the art that thepresent invention may be practiced without these specific details. Inother instances, well-known methods, procedures, and components,modules, units and/or circuits have not been described in detail so asnot to obscure the invention. Some features or elements described withrespect to one embodiment may be combined with features or elementsdescribed with respect to other embodiments. For the sake of clarity,discussion of same or similar features or elements may not be repeated.

Although embodiments of the invention are not limited in this regard,discussions utilizing terms such as, for example, “processing,”“computing,” “calculating,” “determining,” “establishing”, “analyzing”,“checking”, or the like, may refer to operation(s) and/or process(es) ofa computer, a computing platform, a computing system, or otherelectronic computing device, that manipulates and/or transforms datarepresented as physical (e.g., electronic) quantities within thecomputer's registers and/or memories into other data similarlyrepresented as physical quantities within the computer's registersand/or memories or other information non-transitory storage medium thatmay store instructions to perform operations and/or processes. Althoughembodiments of the invention are not limited in this regard, the terms“plurality” and “a plurality” as used herein may include, for example,“multiple” or “two or more”. The terms “plurality” or “a plurality” maybe used throughout the specification to describe two or more components,devices, elements, units, parameters, or the like. The term set whenused herein may include one or more items.

Unless explicitly stated, the method embodiments described herein arenot constrained to a particular order in time or to a chronologicalsequence. Additionally, some of the described method elements can occur,or be performed, simultaneously, at the same point in time, orconcurrently. Some of the described method elements may be skipped, orthey may be repeated, during a sequence of operations of a method.

Reference is made to FIG. 1, showing a non-limiting block diagram of acomputing device or system 100 that may be used to operate a storagesystem according to some embodiments of the present invention. Computingdevice 100 may include a controller 105 that may a hardware controller.For example, computer hardware processor or hardware controller 105 maybe, or may include, a central processing unit processor (CPU), a chip orany suitable computing or computational device. Computing system 100 mayinclude a memory 120, executable code 125, a storage system 130 andinput/output (I/O) components 135. Controller 105 (or one or morecontrollers or processors, possibly across multiple units or devices)may be configured (e.g., by executing software or code) to carry outmethods described herein, and/or to execute or act as the variousmodules, units, etc., for example by executing software or by usingdedicated circuitry. More than one computing devices 100 may be includedin, and one or more computing devices 100 may be, or act as thecomponents of, a system according to some embodiments of the invention.

Memory 120 may be a hardware memory. For example, memory 120 may be, ormay include machine-readable media for storing software e.g., aRandom-Access Memory (RAM), a read only memory (ROM), a memory chip, aFlash memory, a volatile and/or non-volatile memory or other suitablememory units or storage units. Memory 120 may be or may include aplurality of, possibly different memory units. Memory 120 may be acomputer or processor non-transitory readable medium, or a computernon-transitory storage medium, e.g., a RAM. Some embodiments may includea non-transitory storage medium having stored thereon instructions whichwhen executed cause the processor to carry out methods disclosed herein.

Executable code 125 may be an application, a program, a process, task orscript. A program, application or software as referred to herein may beany type of instructions, e.g., firmware, middleware, microcode,hardware description language etc. that, when executed by one or morehardware processors or controllers 105, cause a processing system ordevice (e.g., system 100) to perform the various functions describedherein.

Executable code 125 may be executed by controller 105 possibly undercontrol of an operating system. For example, executable code 125 may bean application that operates or manages a storage system as furtherdescribed herein. Although, for the sake of clarity, a single item ofexecutable code 125 is shown in FIG. 1, a system according to someembodiments of the invention may include a plurality of executable codesegments similar to executable code 125 that may be loaded into memory120 and cause controller 105 to carry out methods described herein. Forexample, units or modules described herein, e.g., each of dataapplication 210, core module 220 and media access module 230, may be, ormay include, controller 105, memory 120 and executable code 125.

Storage system 130 may be or may include, for example, a hard diskdrive, a universal serial bus (USB) device or other suitable removableand/or fixed storage unit. As shown, storage system 130 may include tagsets or groups 131, data block names 132 and data blocks 133(collectively referred to hereinafter as tag sets 131, data blocks 133and/or data block names 132 or individually as a tag set 131, a datablock 133 and/or a data block name 132, merely for simplicity purposes).

Although shown as separate objects, tag sets 131 and data block names132 may be included in one or more objects, e.g., in a database, suchthat given a tag set 131, the associated data block name 132 can bequickly identified, located and/or retrieved. Likewise, tag sets 131 anddata block names 132 may be stored such that given a data block name132, all a tag sets 131 associated with the data block can be readilyand quickly identified, located and/or retrieved.

As referred to herein, associating a tag set 131 (or a data block name132) with a data block 133 may include generating, including orarranging digital information (e.g., in a database in storage system130) such that given a tag set 131, an associated data block 133 can bequickly found and/or retrieved. For example, associating a tag set 131with a data block 133 may include adding a pointer or reference to thetag set 131 or associating a tag set 131 with a data block 133 may beachieved by including the tag set 131 and a reference to the data block133 in the same entry or row in a table, list or database. It will beunderstood that the scope of the invention is not limited by the way tagsets 131 are linked to, or associate with, data blocks 133.

Tag sets 131 and data block names 132 as referred to herein may be anysuitable digital data structures, constructs or computer digital dataobjects that enable storing, retrieving and modifying values. Forexample, tag sets 131 and data block names 132 may be, or may beincluded in, files, tables or lists in a database in storage system 130,and may include a number of fields that can be set, modified, clearedand so on. For example, entries may be added to a table or list toindicate or represent an association of a data block with a tag asfurther described herein.

Data blocks 133 may be any suitable object usable for storing digitalinformation, for example, a data block may be a number of contiguousbytes in a hard disk, an object stored in a block or object storagesystem or any chunk of digital data. It will be noted that, in someembodiments, tag sets 131 and data block names 132 are stored in a firststorage system or device and data blocks 133 are stored in a second,different storage system or device. For example, tag sets 131 and datablock names 132 may be stored in a fast (possibly expensive) storagesystem and data blocks 133 may be stored in mass storage device that maybe slower but cheaper. A mass storage device may be, for example, adevice similar to storage system 130 that may be optimized for storagecapacity but not necessarily for speed.

Content may be loaded from storage system 130 into memory 120 where itmay be processed by controller 105. For example, a tag set 131 may beloaded into memory 120, controller 105 may add a tag to the tag set 131in memory 120 to produce an updated tag set 131 and then store theupdated tag set in storage system 130.

I/O components 135 may be, may be used for connecting (e.g., viaincluded ports) or they may include: a mouse; a keyboard; a touch screenor pad or any suitable input device. I/O components may include one ormore screens, touchscreens, displays or monitors, speakers and/or anyother suitable output devices. Any applicable I/O components may beconnected to computing device 100 as shown by I/O components 135, forexample, a wired or wireless network interface card (NIC), a universalserial bus (USB) device or an external hard drive may be included in I/Ocomponents 135.

A system according to some embodiments of the invention may includecomponents such as, but not limited to, a plurality of centralprocessing units (CPU) or any other suitable multi-purpose or specificprocessors, controllers, microprocessors, microcontrollers, fieldprogrammable gate arrays (FPGAs), programmable logic devices (PLDs) orapplication-specific integrated circuits (ASIC). A system according tosome embodiments of the invention may include a plurality of inputunits, a plurality of output units, a plurality of memory units, and aplurality of storage units. A system may additionally include othersuitable hardware components and/or software components. A system mayinclude or may be, for example, a workstation, a server computer, anetwork device, or any other suitable computing device.

Embodiments of the invention may include a data storage OS that providescontext based interface and operations related to data. As described,sets of tags and unique names associated with data blocks may be usedfor providing clients of a system with a context based view andinterface, thus enabling clients of a system to request and receiveservices based on any logical context of the data and further relievingclients from having to deal with details of an underlying storagesystem. When used herein, a name that is “unique” is typically within asystem or set of names according to an embodiment of the invention.

Reference is made to FIG. 2, an overview of a storage control system 200and flows according to some embodiments of the present invention. Asdescribed, system 200 or components of system 200 may be, or mayinclude, components such as those shown in FIG. 1.

As shown, system 200 may include a data application module 210, a coremodule 220, a media access module 230, a plurality of storage devicedriver modules 240-A, 240-B and 240-C, and system 200 may include or maybe connected to a plurality of storage devices or systems 30-A, 30-B and30-C. Of course, in some embodiments, only one, single storage devicedriver (e.g., module 240-A) is included in system 200 and may be used,e.g., to operatively connect system 200 to a single storage device(e.g., storage device 30-A).

Computing devices 20-A and 20-B may be any suitable computing device (eg, similar to computing device 100) and may be used by clients of system200. Clients of system 200 may be, for example, users who store/retrievedata in/from system 200 and/or applications that store/retrieve datain/from system 200 and/or devices, e.g., computing devices 20-A and 20-Bas shown in FIG. 2. For example, computing device 20-A may be used by auser or application to store and/or retrieve data from system 200 asdescribed herein.

In some embodiments, core module 220 associates data blocks 133 with oneor more tag sets 131. A tag set 131 may represent, or include, a contextof and/or other attributes of the data block 133 with which it isassociated. Generally, a context may include, or be determined ordefined based on, any relevant or applicable attribute or aspect, e.g.,a context may be, may include, or may be defined based on, one or moreof: an indication or identification of a storage media, e.g., a name, ora reference to, a data volume, a hard drive or other applicable media orstorage system or object; a name or other reference to a digital contentobject; an offset in a data block; a date and time or timestamp value; asource of data block; a type of the actual data or content in a datablock; a usage of data in a data block etc. It is noted that since acontext may be represented by tag sets, and tags to be included in tagsets may be freely defined, any user-defined context, dynamically orautomatically defined context, or other contexts may be defined and usedby a system as described.

For example, a first tag set 131 may be created for a context of a firstapplication (e.g. a program, a software module, an instance of aprogram, etc.) or user and may be associated with a data block 133 and asecond tag set 131 may be created for a second application or user andmay be associated with the same data block 133. Accordingly, a pluralityof tag sets 131 may be associated with a single data block 133 thusenabling different views, makings or usages of a single data block.

In some embodiments, a tag set 131 includes a set of tags that togetherrepresent a logical context or other attribute of data, with respect toa user, application or owner of at least a portion of a data block 133.For example, a first tag set 131 may be created for a first applicationand may be associated with a first offset in a data block 133 (e.g., thefirst offset is where the data of interest for the first application isstored within the data block 133) and a second tag set 131 may becreated for a second application and may be associated with a secondoffset in the same data block 133, e.g., since that is where data ofinterest for the second application is stored. Accordingly, tag sets asdescribed provide a virtualization layer on top of data blocks providingeach client of a storage system with its own view of the storage system.

Reference is made to FIG. 3, which shows tag sets associated with a datablock. As further described herein, associating a tag set 131 and/or adata block name 132 with a data block 133 may include creating andarranging digital information such that a tag set 131 and/or a datablock name 132 is/are linked to data block 133. As described, anassociation of a tag sets with a data blocks enable finding, retrievingor obtaining a data block given, or based on, a tag set, an associationas described may enable finding, retrieving or obtaining a tag set basedon a data block.

As shown, a plurality of tag sets 310, 320 and 330 may be associatedwith a single data block 133 and each tag set represents a differentcontext of the data block. As further shown, each of the tag setsinclude a set of tags. For example, and as shown in FIG. 3, tag set 310includes a block volume name or reference (first tag in the tag set) andan offset in the data block 133 (second tag in the tag set) and tag set330 also includes two tags, an indication or type of a file and areference to a data chunk in data block 133. Although block or datavolume is mainly referred to herein, for simplicity, it will beunderstood that any media and/or object may be used where applicable,e.g., a file, a hard disk segment or any application specific entity.

It will be understood that any number of tag sets 131 can be associatedwith a single or same data block 133. For example, when a newapplication or user starts using system 200, a new tag set 131 may becreated for the new user or application and the new tag set 131 may beassociated with data blocks provided by the new user or applicationand/or the new tag set 131 may be associated with data blocks that mayhave been stored in the system long before the new user or applicationstarted using the system.

Although only two tags are shown in each of tag sets 310, 320 and 330,it will be understood that any number of tags may be included in a tagset 131. For example, tags related to time, user or application name,location in storage, type of content and the like may be included in atag set. Accordingly, any relevant aspect of, or context related to datain a data block may be reflected, represented or included in a tag set131 as described herein, and, a given block of data can have multiplelogical contexts associated with it (using tag sets as described) whereeach context represents a different aspect, e.g., different applicationor different regions in the data associated with a given application.

In some embodiments, tag sets 131 are associated with names of, or otherreferences to, data blocks 133. For example, tag sets 131 may beassociated with globally, or system unique names that are generated fordata blocks 133. A unique name as referred to herein may be uniquewithin a specific instantiation of the invention, but not be unique whencompared with the universe of names of data blocks stored on allexisting computer systems. For example, a secure hash generated based onthe content of a data block 133 may be, or may provide, a globallyunique name for the specific data block 133 in a storage system. Aunique name or reference for a data block may be defined and generatedbased on the actual content of a data block 133.

Reference is made to FIG. 4, showing association of tag sets with a datablock name. As shown, a name 410 for data block 133 may be generated,e.g., by core module 220, by calculating a secure hash value that may beunique for the content in data block 133. Accordingly, if the content ina first and second data blocks 133 is different than the namescalculated for the first and second blocks will be different, similarly,the same names may be generated for two different data blocks 133 if thedata blocks include identical content. Any method for generating uniquenames or references for data blocks may be used. It will be understoodthat a unique name as referred to herein may be unique within a specificinstantiation of the invention, but not be unique when compared with theuniverse of names of data stored on all existing computer systems.

In some embodiments, names of data blocks 133 and their associated tagsets are stored in a tag database, e.g., included in or operativelyconnected to, data core module 220. Using a database that includes (andassociates) unique names of data blocks 133 and associated tag sets 131,core module 220 (or a database therein) may support various operationsor interfaces. For example, core module 220 may receive a request thatincludes a tag or tag set and respond with an associated name or acombination of a name and tag set. In another example, core module 220may, in response to a request, add a new name/tag set combination and/oradd a tag to an existing tag set. In yet other cases, core module mayreceive a request (or registration) to be notified when a specific eventrelated to any one of: a name, tag or tag set occurs. For example, auser may request to be notified each time a data block 133 associatedwith a specific tag set is accessed or retrieved.

Reference is made to FIG. 5, showing a conceptual representation of adatabase according to illustrative embodiments of the present invention.As shown by table 510, each entry may include a tag set 131 and name ofthe data block 133 associated with the tag set. It will be understoodthat any number of additional columns may be added to table 510 toenable any size or number of tags in a tag set. Entries in table 510 mayinclude metadata, e.g., metadata included, per entry, in database 510,may be a sequence number that may represent order of entries in time, atimestamp and so on. An arrangement of data as illustrated in FIG. 5enables various operations and services, e.g., search for, retrieveand/or provide all data blocks 133 associated with a specific tag set131, search for, retrieve and/or provide all tag sets 131 associatedwith a specific data block 133 and so on. Other operations or servicesperformed or provided by embodiments using a database as illustrated bytable 510 may be providing data block names in response to a tag (e.g.,all data blocks associated with a tag), adding new <name, tag set>entries and add tags, adding new tags to existing tag sets, alert usersor applications when an event occurs based on a registration, e.g., aregistration for a specific tag set, data block name and/or a specificevent.

Storage of the actual data (the data or content in/of data blocks 133)may be performed by media access module 230 and one of drivers 240-A,240-B and/or 240-C. Generally, media access module or layer 230 providesa mechanism to store and access data from different types of media witha single common interface that is independent of the details of theunderlying media. The individual media drivers (e.g., drivers 240-A,240-B and/or 240-C) deal with the details of the supported media types.

In some embodiments, media access layer 230 provides (or exports)functions that allow the storage and retrieval of arbitrary sized datablocks. For example, media access layer 230 may, based on a request thatincludes data and a name, store a data block with a name, or, providedwith a name, media access layer 230 may retrieve a data block associatedwith the name. Any other operations related to data blocks, names andtag sets may be performed.

In some embodiments, media access layer 230 handles the storage of theactual data blocks using media drivers (e.g., drivers 240-A, 240-Band/or 240-C). In some embodiments, media access layer 230 provides amechanism to store and access data, on/from any type of media, with asingle common interface that is independent of the details of theunderlying media. The individual media drivers (e.g., drivers 240-A,240-B and/or 240-C) deal with the details of the supported media types.In some embodiments, media access layer 230 exports, supports orprovides functions that allow the storage and retrieval of arbitrarysized data blocks.

Reference is made to FIG. 6, showing a conceptual representation of amedia access layer according to illustrative embodiments of the presentinvention. As shown, the underlying media may be flash storage handledby a flash drive, a cloud based storage handled by a suitable driveretc. As further illustrated in FIG. 6, media access layer 230 mayprovide a storage service (or storage operation, function or process)that receives a name and a data block, records the name and stores theactual data (content of the data block) in one or more of the underlyingmediums. For example, a name received by media access layer 230 may beas shown in the “Name” column in the table shown in FIG. 5 and a datablock received may be the digital content of a data block 133 asdescribed. As further shown, media access layer 230 may provide aretrieve function that receives a name and, in response, provides thedata block (or the content of the data block 133) associated with thename. More than one data block may be provided in response to a requestthat includes more than one names. For example, computing device 20-Amay be an external device that sends a request to system 200, e.g., arequest to retrieve data from, or a request to store data in, system 200and system 200 may, in response to a request from computing device 20-A,provide a number of data blocks, e.g., from storage devices 30-A and30-C or store a number of data blocks, e.g., in storage devices 30-A and30-B.

Likewise, a plurality of data blocks may be provided in a single storerequest. Accordingly, access layer 230 may support or provide a set orplurality of store and/or retrieve operations for multiple data blocksand/or names based on a single request.

In some embodiments, core module 220 and media access module 230, alongwith the drives such as drivers 240-A, 240-B and/or 240-C form a dataOS. The set of functions exposed, provided and described herein, by thetag or tag set database and media access module 230 forms theapplication programming interface (API) of the data OS. Higher levelAPIs that, for example, automatically generate names for data when astorage request is made, chunk data into smaller blocks, compress data,and then invoke requests to both core module 220 and/or media accessmodule 230 may all be provided by the data OS. Data applications can usethe interfaces provided by the data OS to store and retrieve datamanaged by the data OS, and to provide management functions for datastored in a data storage infrastructure based on the data OS.

An example of a data application may be a block storage target thatsupports a specific block protocol, e.g., Internet Small Computer SystemInterface (iSCSI). In this example, the iSCSI target data applicationterminates the iSCSI connection and all further data operations are doneusing the data OS API.

Reference is made to FIG. 7, which shows a write operation to an iSCSIblock storage target according to illustrative embodiments of thepresent invention. As shown by block 710, data to be stored may bereceived, e.g., system 200 receives data from computing device 20-A. Asshown by block 720, data received may be divided (e.g. broken orchunked) into smaller portions or blocks and names may be generated forthe portions, chunks or blocks, e.g., using a function that generates aunique name or code based on the actual content of a data block asdescribed. As further shown, data blocks may be compressed either beforeor after unique names are generated.

As shown by block 730, sets of tag sets and names may for the portions,chunks or blocks may be added to a database, e.g., new entries may beadded to table 510 as described herein. As shown by block 740, the dataportions, chunks or blocks may be stored in association with theirnames, e.g., by calling or invoking media access module 230 to performthe actual storage and providing media access module 230 with names anddata blocks.

For example, a data block to be stored may be received by system 200(e.g., from an application 921 described herein with reference to FIG.9), system 200 may create a set of tags (tag set) based on informationincluded in the request for storing the data block and may associate thetag set with a unique name. For example, a request to store a data blockmay include a file name, a volume/offset combination, a size and thelike and any part of the information in a request may be used forcreating a tag set as described. A system may further generate a uniquename for the data block and associate the unique name with the tag set,e.g., by including the unique name in an entry that includes the tag setas described. It is noted that associating a unique name with one ormore tag sets may be done using any technique, e.g., pointers may beused. When a request for retrieving the data block is received, system200 may identify the tag set based on information in the request. Forexample, a file name in a request may be used to find the relevant tagset since, as described, a tag may include a file name, or it may becreated such that it can be matched with file name, e.g., to savestorage space and/or increase performance, a tag may include a hashvalue generated based on a file name. Having identified the correct tagor tag set, a unique name of the data block may be readily obtainedsince, as described, the unique name may be associated with the tag, theunique name may be used for locating and/or retrieving the data block orprovide any other service related to the request, e.g., copy the datablock, delete the data block and so on.

Another example of a data application may be an application that copiesdata according to a point in time, from a block volume (or any otherstorage system, device or media) to another storage device, system ormedia. For example, a time tag or timestamp, for each data block 133,may be included in a database, e.g., as illustrated by table 510.Accordingly, an embodiment can find or identify data blocks according totime, e.g., find data blocks that were modified in the last 24 hours,stored in the last week and so on.

Reference is made to FIG. 8, showing a flow of copying data stored in afirst (source) storage device, system or media to a second (destination)device, system or media. As shown by block 810, a data volume (or anyother storage system, device or media) identifier and a time stamp orindication may be used to query a database (e.g., a database includingdata as shown by table 510). As shown by block 820, an embodiment (e.g.,core module 220) may respond to the query with a list of blocks (andtheir associated names) that were stored or modified on or before thetime indicated in the query. For example, using information in table 510that may include a timestamp as described and a tag that identifies adata volume (or any other storage system, device or media), core module220 can find all relevant data blocks as described. As shown by block830, an embodiment may, for each name included in the response, providethe name to media access module 230 and command media access module 230to copy the associated data block from the source device or system tothe target device or system.

As described, embodiments for managing a storage system may includegenerating, for a data block, a set of tags (e.g. tag set) and a uniquename; associating the tag set and unique name in a database; receiving arequest including at least one tag; and providing at least one servicerelated to the data block based on the received tag, tag set and uniquename. For example, and as described, core module 220 may generate aunique name for a data block based on the content in the data block,generate or receive a set of tags and store the unique name and set oftags in a database such that the unique name and set of tags areassociated or linked. Using services provided by media access module230, core module 220 may provide services or interfaces based on tagsets and/or unique names.

An embodiment may store a data block in a storage system and mayassociate information usable for retrieving the data block with theunique name. For example, media access module 230 may receive a datablock to be stored and a unique name of the data block, store the datablock in a storage system or media and record an association of thelocation of the data block in the storage system with the unique name.Accordingly, given a unique name, media access module 230 may retrievethe data block from the storage system. Media access layer 230 mayperform deduplication of data based on names generated and associatedwith data blocks as described, for example, by storing a given datablock only once if/when multiple store operations are received with thesame name.

An embodiment may perform an action related to a data block based onmatching (e.g. comparing and determining whether or not the data isidentical) data in a request with data in a tag set. For example,specific fields or values in a request from computing device 20-B may beextracted and compared to data in a tag set, if a match is found, thatis, the extracted values are same as those in a tag set, the associateddata block may be retrieved as described, if a match is not found thenan embodiment may perform one or more actions, e.g., a new tag set maybe created or the request may be responded with an error message or anerror may be logged.

For example, a request may include a set of tags and core module 220 maysearch for all tag sets that match or are the same as the set of tags inthe request and perform an action related to one or more data blocksassociated with the matching tag sets.

An embodiment may automatically and/or dynamically modify a tag set. Forexample, tags may be added, removed or modified to/in tag sets alreadystored as described such that tag sets are not fixed but are dynamic,e.g., change or evolve as data in storage system 200 changes. Forexample, when a context is changed, e.g., an owner of data has changed,permissions to access data changed and so on, then core module 220 maymodify tag sets associated with the data such that the new context isreflected by the modified tag sets.

An embodiment may associate a data block with a plurality of tag sets,for example, as shown by FIG. 5 and described herein. For example, anassociation of a data block 133 with a tag set 131 may be, or mayinclude, including the tag set 131 (or at least some of the data in atag set) and a reference to the data block 133 in the same row of atable or same entry in a list as illustrated in FIG. 5. As furtherillustrated in FIG. 5, a single or same data block 133 may be associatedwith any number of tag sets, e.g., using a set of entries in a list ortable that associate a data block 133 with a respective set of tag sets.For example, and as shown in FIG. 5, the data block 133 referenced by“0xFB092EE5” may be associated with three different tag sets.Accordingly, a data block may be searched for, selected, used, viewed ormanipulated according to a number of different contexts represented by arespective set of tag sets.

An embodiment may alert or notify a client based on a registration, theregistration including at least one tag. For example, a client, e.g., anoperator of, or an application on, computing device 20-B may register tobe alerted if data that is associated with a specific tag or tag set ismodified, deleted or accessed and system 200 may, if any data blockassociated with the tag or tag set indicated in the registrationrequest, is modified, deleted or accessed, alert the operator orapplication. A client may be considered to be a person operating anapplication, program or computer, that makes a request, and/or theapplication, program or computer making the request.

An embodiment may use tag sets or groups and unique names to automate aprocedure related to at least one of: data backup, data restore, datacopy, periodic maintenance operation and data retention. For example,data application 210 may backup all data blocks associated with aspecific tag, perform a retention operation based on tags and so on.

A service provided, executed or performed; or denied, by an embodimentbased on a logical context defined by a tag set. For example, although arequest to delete data is received, an embodiment may refuse deletion ofthe data because it is associated with a specific tag. In other cases,an embodiment may change all data blocks associated with one or moretags to read-only thus protecting data based on tags or context.

A service or operation may be executed, performed or selected; or anoperation may be refused or denied, based on a context rule applied to aset of tag sets. For example, a context rule may indicate that dataincluding images, stored before Jul. 19, 2017 and used by a specificapplication must not be deleted. As described, using tag sets, applying(possibly very complex) rules, may be readily performed by embodimentsof the invention.

An embodiment may include a layer adapted to provide an interface with amedia storage system based on the unique name and the data. For example,a layer in system 200 may provide an interface for storage devices 30-Aand 30-B where the interface uses unique names, e.g., a data blockstored in storage device 30-C is provided, by the interface layer, inresponse to a unique name.

An embodiment may include a core unit, module or layer adapted togenerate and maintain tag sets and unique names, e.g., core module 220and a media layer adapted to store and retrieve data blocks according tothe unique names, e.g., media access module 230. Generally, a unit,module or layer as referred to herein may be, or may include, a set ofinstructions or a logic executed by controller 105. An embodiment mayfurther include an Application Programming Interface (API) combininginterfaces of the core layer and the media layer. For example, inresponse to a request from a client, APIs of system 200 may sendcommands or requests to core module 220 and media access module 230 andgenerate and provide a response to the client based on responsesreceived from core module 220 and media access module 230. Accordingly,an embodiment may provide a unified interface for a core module and amedia module.

A system comprising core module 220, media access module 230, devicedrivers 240 and storage devices 30 was described herein, otherembodiments and/or configurations may be contemplated. Reference is madeto FIG. 9 showing a system 900 and flows according to illustrativeembodiments of the present invention. As shown, system 900 may interactwith applications 920 and 921 that may be executed on computing device20-A and computing device 20-B shown in FIG. 2. As further shown, system900 may include a pitcher unit 930, a local cache 940, a catcher unit950, a metadata (MD) keeper unit 960, and a plurality of fast keeperunits 970. Although only two fast keepers 970 are shown it will beunderstood that any number of fast keepers 970 may be included in orconnected to a system according to embodiments of the invention. One offast keepers 970 may be individually referred to herein as a fast keeper970, merely for simplicity purposes.

In some embodiments, operations, logic and components included in coremodule 220 may be performed or included in pitcher 930. For example,pitcher 930 may be the front end of system 900. For example, to performa write operation, application 920 may send tag data (e.g. metadata) anddata (e.g. payload) to pitcher 930 as shown, e.g., as part of a requestto store or write the payload data. Tag data may be any metadata usablefor generating tags and tag sets as described herein. Tag data providedby application 920 may be any metadata related to the data provided forwrite or store. Tag data provided by application 920 may be accordingto, or based on a protocol and/or an application. Generally, tag dataprovided by application 920 may be structured according to a nativelanguage or protocol of application 920. Accordingly, system 900 mayprovide a first native interface for a first application (e.g.,application 920) and system 900 may further provide a second nativeinterface for a second application (e.g., application 921).

For example, application 920 may be an application that uses keys toaccess objects in a database, that is, the native language or interfaceof application 920 includes, or is based on keys as known in the art,and, application 921 may be an application that uses objects'identifiers for retrieving objects, e.g., from an object-based storage,that is, the native language or interface of application 921 includes,or is based on unique object identifiers (IDs), yet another applicationthat can readily interface with system 900 may use, as its nativelanguage or interface, combinations of volume IDs and offsets, and, anadditional application interfacing with system 900 may use file names.Accordingly, using a set of tags (e.g. tag group or set) that areassociated with data chunks, blocks or other objects, system 900 caninterface with any application or system, allowing the applications thatinterface with system 900 to maintain their native or natural languageor protocol.

Providing a storage system (e.g., system 900) that can interact orinterface with a set of different applications that use a respective setof different protocols or interface schemes, without requiring theapplications to be modified, configured or adjusted is an improvement ofthe technological field of computer data storage. Using tag sets asdescribed may enable system 900 to be easily adapted or configured toprovide data storage service to any application or system, e.g.,provided with details of a protocol or scheme used by an application,tag sets may be created, set and used as described such that requestscoming from the application are serviced without any change to theapplication. A practical application of an embodiment of the inventionmay be, for example, system 900 that may, as described, generate, for adata block, a set of tags (e.g. tag set) and a unique name, for example,a data block received from application 920 may cause pitcher 930 tocreate a set of tags and associate the data block with the set of tags.A practical application of an embodiment of the invention may furtherassociate the data block and/or the set of tags with a unique name,identification code, string or value. A practical application of anembodiment may receive a request including at least one tag, e.g.,system 900 may receive a request related to a data block stored insystem 900 from application 920 where the request includes informationthat can be translated or related to one or more tag sets as described,and the application may provide at least one service related to the datablock based on the received tag information, and based on the uniquename, identification code, string or value.

As further described herein, by separating the actual storage of datafrom the interface with applications, an embodiment of the invention canprovide native interfaces to a plurality of application types whileusing the same efficient storage layer.

As shown, based on the data (e.g. payload) and the tag data, pitcher 930may calculate or determine a unique name for the payload and a tag set.The tag set calculate or determine may be, for example, tag set 310 asdescribed herein and the unique name may be as shown by block 410 anddescribed herein or the unique name and tag set may be as shown in FIG.5 and described herein.

As shown, the data (e.g. payload), unique name and tag set may bewritten to a local cache 940. As further shown, pitcher 930 select oneof fast keepers 970 and may provide the data (payload) received fromapplication 920 and the unique name to the selected fast keeper. In someembodiments, operations, logic and components included in storage devicedrivers 240-A, 240-B and 240-C and operations, logic and componentsincluded in storage devices 30-A, 30-B and 30-C may be performed by,connected to, or included in, fast keepers 970. For example, fastkeepers 970 may be very fast and efficient since they operate based onan association of a unique name with a data block, that is, fast keepers970 are unaffected by, or are indifferent to, aspects such as context,application that is the source of the data and so on.

As shown, pitcher 930 may provide the unique name and tag set to catcherunit 950 that may use a metadata keeper 960 to store the unique name andtag set. For example, data shown in table 510 may be stored by metadatakeeper 960.

Reference is made to FIG. 10 showing a system 900 and flows according toillustrative embodiments of the present invention. As shown, to readdata from system 900, application 920 may send tag data to pitcher 930.For example, tag data may be a combination of a table name, row andcolumn identifying a data element that application 920 wants to read.Pitcher 930 may use the tag data to calculate a tag set and then use thetag set to check whether or not the requested data is in cache 940 asshown by the arrow extending from pitcher 930 to local cache 940. Cache940 may store the actual data (payload) and/or it may store a mapping oftag sets to unique names. Accordingly, as shown by the arrow extendingfrom cache 940 to pitcher 930, cache 940 may return the requested dataand/or cache 940 may return the unique name of the requested data. Incases where the actual requested data (payload) is stored in cache 940and is returned from cache 940 to pitcher 930 then pitcher 930 may sendthe requested data to application 920 thus completing the read cycle.

In cases where the unique name is not found in cache 940, pitcher 930may send the tag set to catcher 950. Generally, catcher 950 is ametadata management unit that stores an association of tag sets andunique names (e.g., data as shown in table 510). Accordingly, providedwith a tag set, catcher 950 may return a unique name to pitcher 930 asshown by the arrow extending from catcher 950 to pitcher 930. Providedwith a unique name, pitcher 930 can now send the unique name to keeper950 as shown and receive, from keeper 970, the actual (requested). Aread cycle may be completed by sending the requested data to application920.

System 900 may perform and/or maintain deduplication of data based onunique names generated and associated with data blocks as described. Forexample, system 900 may store one, and only one, data block per uniquename even if multiple store operations are received with the same name.Since a unique name of a data block may be calculated based on thecontent of the data block (e.g., the unique name may be a hash valuecalculated based on the actual content (payload) of a data block), iftwo or more data blocks have (or are associated with) the same uniquename that means that the contents (payload) of the two or more datablocks are identical, that is, the two or more data blocks areduplicates. Accordingly, by identifying data blocks with the same uniquenames system 900 may identify duplicates, by keeping one, and only one,data block associated with a given unique name system 900 may ascertainthat no duplications exist in the system.

For example, pitcher 930 may receive data from application 920, breakthe data into data blocks and then calculate a unique name for each datablock. Pitcher 930 may then select, based on the unique names, keepers970 for storing each of the data blocks. For example, unique names maybe, or may include, a value, thus, a first keeper 970 may be selected ifthe value included in a unique name is in the range of 0-99, a second,different keeper 970 may be selected if the value included in a uniquename is in the range of 100-199 and so on. Selecting a keeper 970 basedon a mapping or unique name ranges as described enables scalability thatcannot be achieved by systems and methods known in the art. For example,to add keepers 970 to system 900, the above mapping example of rangescan be changed, e.g., instead of two keepers 970 for the range of 0-199in the above example, three keepers 970 can be used for ranges 0-75,76-140 and 141-199.

Keepers 970 may discard any duplicates by identifying two or more datablocks with the same unique name and removing data blocks such that oneand only one data block associated with the unique name is kept bysystem 900. It is noted that performing deduplication based on uniquenames as described is very fast and efficient compared to system andmethods that need to compare payloads in order to deduplicate a storagesystem. Otherwise described, system 900 may remove redundant data blocks(deduplicate) without comparing content of data block. The advantage ofdeduplication based on unique names as described over systems andmethods that need to compare the actual payload of data blocks will beappreciated by a person with ordinary skill in the art.

A mapping of unique name ranges to keepers 970 as described enables fastretrieval if data. For example, equipped with a unique name, pitcher 930can readily send a retrieve command to the relevant keeper 970 which, asdescribed, can perform a retrieve or read operation extremely fast.Accordingly, a read cycle of system 900 includes a minimal set of simpleoperations e.g., determining unique name, read data of unique name. Insome embodiments, local cache 940 may store data blocks in associationwith their respective unique names, e.g., in a way similar to the waykeepers 970 store data. Accordingly, a read cycle based on a unique namemay be completed without having to interact with keepers 970.

It is noted that cache 940 may be used for retrieving the actual (e.g.cached) data as described and/or may be used for caching an associationof unique names and tag sets. For example, a copy of table 510 may bestored in cache 940 thus enabling cache 940 to provide pitcher 930 witha unique name based on a tag set received from pitcher 930.

Either pitcher 930 or keeper 970 may compress and/or encrypt a datablock prior to storing the data block. Either pitcher 930 or keeper 970may decompress and/or decrypt a data block prior to providing the datablock to application 920. Pitcher 930, local cache 940, catcher 950 andkeepers 970 may be executed on a single, same device 100 or they mayeach be executed on its own device 100. A single catcher 950 may serve anumber of pitchers 930, e.g., store tag sets associations with uniquenames for two or more pitchers 930. A single metadata keeper 960 mayserve any number of pitchers 930. In the capacity of metadata storage,catcher 950 may store any metadata, e.g., a history of reads, writes,transactions or any other logs.

Some known storage systems and methods support a specific protocol orlanguage, e.g., an object-based storage system supports object IDs butdoes not support volume/offset referencing, accordingly, such storagesystems and methods force applications to adhere to a specific protocolor language, e.g., to use the storage system, an application must bemodified to support the specific protocol or language. Other knownstorage systems and methods support an application-specific protocol orlanguage, e.g., a proprietary storage system is specifically tailored tosupport a protocol that is supported by, or is native to, anapplication.

In contrast, embodiments of the invention, e.g., systems 200 and 900 canserve, or be readily connected to a plurality of applications or systemsthat require storage services and that support a plurality of differentprotocols, languages, schemes or conventions. By adding tag sets andassociating them with unique names as described, systems 200 and 900 canbe easily adapted to support any protocol or interface specifications.Tat sets can be viewed as dictionaries that translate any language,protocol or convention to an internal representation, e.g., one thatincludes the unique names.

Accordingly, embodiments of the invention can easily be adapted orconfigured to serve, or communicate with, any application or systemusing a protocol and/or language that is native to the application orsystem. For example, a data block containing an image of a person may beassociated with a unique name and stored as described. The data blockmay further be associated with one or more tag sets as described. Forexample, a first tag set that includes an object identification (objectID) associated with the data block containing the image may be used whenserving requests from an application that natively uses object IDs,e.g., an object-based storage application as known in the art. A secondtag set that includes a volume ID and offset may be used when servingrequests from an application that natively uses volume-offsetcombinations. Using tag sets association with unique names to providetranslation or adaptation layer as described, embodiments of theinvention provide storage services to any application or system whileusing, for all different applications, protocols or languages, the sameefficient storage layer (e.g., fast keepers 970, storage device drivers240 and storage devices 30).

The above protocol examples of object ID and volume and offsetaddressing are simple ones, it will be understood that far more complexprotocols, conventions or languages are enabled by the invention, e.g.,tag sets that translate any protocol or interface scheme may be readilydefined, set (e.g., in table 510 as described) and used to translaterequests from any application using any protocol, interface scheme orconvention to an internal representation of data blocks such that anembodiment, e.g., system 900 can readily be adapted to interface with,or provide services to, any application using any communication orinterface. Generally, the combination of tag sets and unique names asdescribed may be viewed and uses as a conversion or translation unit,logic or scheme that can translate requests and responses from/to anyapplication thus enabling an embodiment (e.g., system 900) to providedata storage and data retrieval services to any application or systemwhile allowing the application or system to maintain its native languageor interface convention, protocol or scheme.

Yet another advantage and improvement provided by embodiments of theinvention is the separation between the protocol, scheme or conventionused by an application (e.g., applications 920 and 921) and the internalor underlying storage protocol, scheme or convention. For example,natively using files, application 920 may send a file to be stored bysystem 900, system 900 may include the file name and other informationin the request in a tag set and associate the tag set with a unique namethat references a volume/offset combination, accordingly, whileapplication 920 users file names as its native language, system 900 maystore data for application 920 using a volume/offset paradigm,similarly, using tag sets and unique names to map between requests andresponses from/to as application 921, system 900 may use an object-basedstorage system to store and retrieve data for application 921 eventhough application 921 uses volume/offsets as its native language.Accordingly and as described, system 900 may provide an application withservices according (or that comply or conform) to the native language,paradigm or protocol of the application while the actual, or underlyingstorage may be according to a different paradigm or protocol.

As described, embodiments of the invention may be, or may include, acontroller 105 that may be, for example, a CPU. For example and asdescribed, pitcher 930, catcher 950 and/or keepers 970 may be, or may besoftware units executed by, controller 105. However, other embodiments,configurations or implementations may be contemplated. For example, oneor more graphics processing units (GPUs) may be used, e.g., one or moreGPUs may include, or perform functions of, pitcher 930 and/or catcher950.

Reference is made to FIG. 11 which shows a prior art system 1100 and asystem 1150 and flows according to illustrative embodiments of thepresent invention. As shown by prior art system 1100, to access storage1130, GPUs 1120 need to go through CPU 1115. For example, and as shownby the TO arrows connecting GPUs 1120 and CPU 1115, if one of GPUs 1120needs to write data to storage 1130, the GPU sends or passes the data toCPU 1115 who in turn writes the data to storage 1130, similarly, to readdata from storage 1130, GPUs 1120 must use, or go through, CPU 1115.

The abstraction of a storage system enabled by embodiments of theinvention enables GPUs to function as pitcher 930 and/or as catcher 950and thus natively use keepers 970. The separation of the actual storageoperations (read data from a storage device, write data to a storagedevice, delete or modify data) from the interface provided to clientsenabled by embodiments of the invention as described enables eliminatingstorage performance bottlenecks and thus improve a storage system.

Some embodiments of the invention enable multiple GPU direct fabricstorage (DFS). For example, in system 1150, GPUs 1155 may be configuredto perform operations and logic of pitcher 930 and/or of catcher 950 andstorage 1160 may be, or may include, one or more keepers 970. Forexample, to write data to storage 1160, instead of going through a CPU(as required in prior art system 1100, a GPU 1155 may compute a uniquename and send the data and unique name to a keeper 970 included instorage system 1160. A GPU 1155 may further generate tag sets for a datablock and associate the tag sets with unique name, e.g., as describedherein with respect to pitcher 930. To read data, a GPU 1155 may send aunique name to a keeper 970 in storage system 1160. Accordingly,embodiments of the invention enable a GPU to directly access a storagesystem (DFS), without requiring an intermediate CPU. Advantages ofdirect access to storage (or DFS) for GPUs may be readily appreciated,for example, bypassing a CPU as described increases speed of operationsas well as decreases CPU load.

Storage system 1160 may include any number of keepers 970 and a GPU 1155may interact with any number of keepers 970, e.g., based on a firstunique name of a first data block, a GPU 1155 may select a first keeper970 in storage system 1160 and the GPU 1155 may select a second,different keeper 970 based on a second, different unique namecalculated, by the GPU 1155, for a second data block.

In the description and claims of the present application, each of theverbs, “comprise” “include” and “have”, and conjugates thereof, are usedto indicate that the object or objects of the verb are not necessarily acomplete listing of components, elements or parts of the subject orsubjects of the verb. Unless otherwise stated, adjectives such as“substantially” and “about” modifying a condition or relationshipcharacteristic of a feature or features of an embodiment of thedisclosure, are understood to mean that the condition or characteristicis defined to within tolerances that are acceptable for operation of anembodiment as described. In addition, the word “or” is considered to bethe inclusive “or” rather than the exclusive or, and indicates at leastone of, or any combination of items it conjoins.

Descriptions of embodiments of the invention in the present applicationare provided by way of example and are not intended to limit the scopeof the invention. The described embodiments comprise different features,not all of which are required in all embodiments. Some embodimentsutilize only some of the features or possible combinations of thefeatures. Variations of embodiments of the invention that are described,and embodiments comprising different combinations of features noted inthe described embodiments, will occur to a person having ordinary skillin the art. The scope of the invention is limited only by the claims.

While certain features of the invention have been illustrated anddescribed herein, many modifications, substitutions, changes, andequivalents may occur to those skilled in the art. It is, therefore, tobe understood that the appended claims are intended to cover all suchmodifications and changes as fall within the true spirit of theinvention. Various embodiments have been presented. Each of theseembodiments may of course include features from other embodimentspresented, and embodiments not specifically described may includevarious features described herein.

The invention claimed is:
 1. A computer-implemented method of managing astorage system, the method comprising: generating, for a data block, aset of tags and a unique name; associating the set of tags and theunique name in a database; receiving a request including at least onetag; providing at least one service related to the data block based onthe at least one tag, the set of tags and the unique name; generatingand maintaining sets of tags and unique names using a core layer;storing and retrieving data blocks according to the unique names using amedia layer; and combining interfaces of the core layer and the medialayer using an Application Programming Interface (API).
 2. The method ofclaim 1, comprising storing the data block in a storage system andassociating information usable for retrieving the data block with theunique name.
 3. The method of claim 1, comprising performing an actionrelated to the data block based on matching data in a request with datain the set of tags.
 4. The method of claim 1, comprising dynamicallymodifying the set of tags.
 5. The method of claim 1, comprisingassociating a data block with a plurality of sets of tags.
 6. The methodof claim 1, comprising alerting a client based on a registration, theregistration including at least one tag.
 7. The method of claim 1,comprising using sets of tags and unique names to automate a procedurerelated to at least one of: data backup, data restore, data copy,periodic maintenance operation and data retention.
 8. The method ofclaim 1, wherein the unique name is generated based on the content ofthe data block.
 9. The method of claim 1, wherein the at least oneservice is selected based on a logical context defined by the set oftags.
 10. The method of claim 1, wherein the at least one service isselected based on a rule applied to a number of sets of tags.
 11. Acomputer-implemented method of providing storage service, the methodcomprising: receiving a data block to be stored; creating a set of tagsand associating the set of tags with a unique name; identifying the setof tags based on information in a request; providing at least oneservice related to the request based on the unique name; generating andmaintaining sets of tags and unique names using a core layer; storingand retrieving data blocks according to the unique names using a medialayer; and combining interfaces of the core layer and the media layerusing an Application Programming Interface (API).
 12. A systemcomprising: a memory; and a controller adapted to: generate, for a datablock, a set of tags and a unique name; associate the set of tags andthe unique name in a database; receive a request including at least onetag; provide at least one service related to the data block based on theat least one tag, the set of tags and the unique name; a core layeradapted to generate and maintain sets of tags and unique names; a medialayer adapted to store and retrieve data blocks according to the uniquenames; and an Application Programming Interface (API) combininginterfaces of the core layer and the media layer.
 13. The system ofclaim 12, wherein the controller is adapted to store the data block in astorage system and associate information usable for retrieving the datablock with the unique name.
 14. The system of claim 12, wherein thecontroller is adapted to provide the data block based on matching datain a request with the set of tags.
 15. The system of claim 12, whereinthe controller is adapted to dynamically modify the set of tags.
 16. Thesystem of claim 12, wherein the controller is adapted to associate adata block with a plurality of sets of tags.
 17. The system of claim 12,wherein the controller is adapted to alert a client based on aregistration, the registration including at least one tag.
 18. Thesystem of claim 12, wherein the controller is adapted to use sets oftags and unique names to automate a procedure related to at least oneof: data backup, data restore, data copy, periodic maintenance operationand data retention.
 19. The system of claim 12, wherein the unique nameis generated based on the content of the data block.
 20. The system ofclaim 12, wherein the at least one service is selected based on alogical context defined by the set of tags.
 21. The system of claim 12,wherein the at least one service is selected based on a context ruleapplied to a set of sets of tags.